-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(thanos): add migration doc for thanos storage clients #16133
Conversation
💻 Deploy preview deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[docs team] Nice job. I added a couple of links, and made some suggestions for revisions, but overall this looks good.
Co-authored-by: J Stickler <[email protected]> Signed-off-by: Ashwanth <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[docs team] Thanks for adding examples, users are always asking for more examples.
Co-authored-by: J Stickler <[email protected]> Signed-off-by: Ashwanth <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[docs team] LGTM.
This PR must be merged before a backport PR will be created. |
Signed-off-by: Ashwanth <[email protected]> Co-authored-by: J Stickler <[email protected]> (cherry picked from commit b63c191)
What this PR does / why we need it:
Adds a migration doc to enable Thanos storage clients. These will replace the existing storage clients in a future release.
I have documented the configuration changes required to migrate clients for commonly used storage backends such as gcs, s3 and azure.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.md
deprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR